Fix sdbus::ObjectPath
when checking signals object_path
#1711
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix deserialization when checking signals
object_path
.Since dnfdaemon: Correct D-Bus signal argument type #1679
sdbus::ObjectPath
is send over to the client notstd::string
.This was causing the check
signature_valid(sdbus::Signal &)
to crash, the client callback ended and the server kept waiting for result of thekey_import
userconfirm.(I believe we should somehow handle when
DbusCallback::signature_valid()
returnsfalse
but I am not sure what would be the best approach. At least logging the event would be good (through thecontext
?).)The other commit fixes a bug for dnf5daemon offline transactions, analogous to dnf5: Run transaction test for offline transactions #1672.